Analysis of Strava activities - Investigating a long bike ride

In this notebook it's presented a focus on a particular Strava activity, in this case a ride: the trajectory is analyzed to better understand how the journey has been carried and which peculiarities it featured (if any).

Data loading

This part is common for all notebooks, for simplicity. It takes all the Strava activities collected and stores them in lists, dataframes, geodataframes and trajectories for every type of activity (runs, hikes, rides and all).

Which are the longest activities in term of time and length? Let's pick the top 5 for both aspects.

Let's check start and arrival points of my longest trip, the activity n° 91.

Starting and arrival point are quite near. This could be a ring trip, but let's check it out by plotting it.

Activity Visualization(s)

So apparently this wasn't a ring trip, but an a/r trip to Garda Lake. Let's investigate more about it.

20 km/h as average pace isn't so bad, but 51 km/h it's definitely out of my capabilities. Where can I have had that peak?

We can see that from Nago to Torbole there is a street portion in which I had a huge pace in a direction, but a really low one in the other direction. Why that?

Excluding the last point, all the others are sequential, so I passed 40 km/h only in that portion of the route. Not really a professional rider, I agree, but can you guess the reason for that pace peak?

That's why: 86m of height difference in less than a km, it's a quite steep descent! But truth be told, I still have clear memories about the ascent on our way back..